Role of a Developer in Starting a Batch of Service Containers

This topic describes the role of an application developer in starting a batch of Service Containers.

An Application Developer plays a vital role in representing the dependencies. A dependency list is determined during the Application creation. This list refers to a set of name spaces on which the application is dependent upon at the start up (namespaces used to invoke any Web service in the open () Web service operation of the Application connector).

• A dependency list is associated with the application connector, hence must be a part of the Application Connector configuration.
  
• The list must not contain namespaces of LDAP and Monitor.
  
• In case of no dependency list, Monitor treats it to be 'no dependency to start the Service Container ' which implies that such a Service Container would be in the initial batches.
  
• Add the startup dependency list as part of the application connector definition similar to 'classpath' addition. The application definition is bundled as a file at installation under <CORDYS_INSTALL_DIR>\XMLStore\collection\Cordys\WCP \Application Connector. As part of the Service creation during installation include the startup dependency.
  
  Sample Configuration
  
  A sample Application connector configuration with startup dependency is listed below. The XML element 'startupDependency' contains all the 'namespaces' that it is dependent on.
  

  <configuration implementation="com.eibus.applicationconnector.myApplicationConnector"> 
  			......
  		<startupDependency>
          <namespace>http://schemas.cordys.com/namespace1</namespace>
          <namespace>http://schemas.cordys.com/namespace2</namespace>
      </startupDependency>
  </configuration>